Article 1649 of rec.games.corewar: Newsgroups: rec.games.corewar From: pk6811s@acad.drake.edu Subject: Re: Nothing new yet Message-ID: <1993Feb22.084906.1@acad.drake.edu> Lines: 113 Sender: news@dunix.drake.edu (USENET News System) Nntp-Posting-Host: acad.drake.edu Organization: Drake University, Des Moines, Iowa, USA References: <85740@hydra.gatech.EDU> Date: Mon, 22 Feb 1993 14:49:06 GMT In article <...> ivner@lysator.liu.se (Anders Ivner) writes: > > loop add const, scan > scan mov jmz loop, > This should work as both an emerald-like bomber and a cmp-scanner, since > something would be found if: > 1) the b-fields of both b and b-1 is non-zero. > or > 2) the b-field of the effective address of " indicate that "a", too, is worth bombing. > Along a similar line is this bomber-scanner called T.Rex. In T.Rex there is a bombing component (line 'stone') into which I drop 2 processes. Note there is no jmp so stone does not grow additional processes. That is to allow the 'scan' component to check the location about-to-be-bombed every 4th or 8th (I can't remember) bomb, just before it is bombed. If the about-to-be-bombed b-field is a 2667-imp, then back up the bomber (it will have advanced past that point now) and change it's increment to 2667. At the same time release some fast replicators. T.Rex works well if the imps are 2667-imps AND they have had time to leave trails of more than a few locations, one or both of which assumptions does not seem to hold on the Hill very much. Also, T.Rex is somewhat of a slow bomber, since one-fourth of the processes in 'stone' are dying at 'dat1' and one additional process is in the scan loop. It does bail out of the scan process after 150 scans. ;redcode quiet ;name T.Rex ;kill T.Rex ;author P.Kline ;strategy stone-paper with a lookout for imps ;strategy added anti-vamp code step equ 2376 boot equ 2000 imp equ 2667 start spl scan,1 ; spl 1,1 spl 1,1 mov